Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add AES256-GCM-SHA384 to the allowed SSL ciphers #1007

Merged
merged 1 commit into from
Nov 9, 2016
Merged

Conversation

ryancragun
Copy link
Contributor

AWS's Clasic ELB health check tool requires this cipher in order to
proxy to Chef Server nodes.

@ryancragun
Copy link
Contributor Author

cc @jeremiahsnapp

@danielsdeleo
Copy link
Contributor

LGTM but I'm not a maintainer. @chef/chef-server-maintainers ?

@stevendanna
Copy link
Contributor

I think this is reasonable, but please add a comment explaining the deviation for mozilla's "modern" advice. cc @lamont-granquist @markan @rhass

@markan
Copy link
Contributor

markan commented Nov 9, 2016

👍 Looks reasonable, but yes, please comment for reason for adding this (so we know when/if to sunset it)

AWS's Clasic ELB health check tool requires this cipher in order to
proxy to Chef Server nodes.

Signed-off-by: Ryan Cragun <[email protected]>
@ryancragun ryancragun merged commit 348ce5e into master Nov 9, 2016
@ryancragun ryancragun deleted the ryan/ZD-12187 branch November 9, 2016 01:26
@lamont-granquist
Copy link
Contributor

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants